Method and apparatus for pairing a mobile device to an output device

ABSTRACT

Methods and systems for associating or pairing a mobile device with a local output device via a central or mobile connect server system are provided. Pairing is performed by initiating a pairing request from an output device that is passed to the mobile connect server for processing. The mobile connect server responds to the request with a pairing code that is displayed by the output device. A user of the mobile device then enters the displayed pairing code in the mobile device. The mobile device transmits the entered pairing code to the mobile connect server and, in response to a match, the mobile device is paired to the output device. Pairing can enable various functions, including an ability to apply stored user preference data to control programming or other information displayed by the output device in response to commands entered in the mobile device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 13/243,491, filed Sep. 23, 2011, which claims the benefit ofU.S. Provisional Patent Application Ser. No. 61/496,702, filed Jun. 14,2011, the entire disclosures of which are hereby incorporated herein byreference.

FIELD

Methods and systems for applying user preferences associated with amobile device to a paired output device are disclosed.

BACKGROUND

Televisions for providing audio-visual entertainment to guests arecommonly available as part of hotel rooms. Often times televisions andother entertainment systems for use in the lodging industry areassociated with distribution systems that permit guests to select from avariety of programming. This programming can include regular off-airtelevision programs, pay per view movies, Internet access, and guestservices such as video shopping and video checkout. In addition, hotelentertainment systems typically include a headend or property managementserver that is located within the lodging facility and that is linked toguest terminals in the individual guest rooms by a distribution system.The local client server generally controls the delivery of selectedcontent to the room terminal, and the application of any associatedcharges to the room bill. In selecting content, the guest typicallyprovides input using a remote control provided as part of theinteractive equipment in the room. Similar systems can be deployed inhospitals or other facilities for the delivery of entertainment or otherservices to patient rooms.

Increasingly, mobile devices, such as mobile telephones or smart phones,are used as a primary interface with communication and entertainmentsystems. These interactive features are often accessed as or throughapplications or “apps” that are resident on the mobile device. Althoughapps can include applications that deliver audio-visual content to theuser, the relatively small format of most mobile devices often providesa less than optimum user experience. Therefore, in a hospitalitysetting, it is desirable to make use of the entertainment equipmentprovided as part of a room's entertainment system. Although variouswireline and wireless communication protocols are available that arecapable of supporting communications between a mobile device and a roomentertainment system, the hardware required to establish such links isoften not a part of existing room entertainment equipment. In addition,simply connecting a user's mobile device to room entertainment deviceshas the effect of merely substituting a conventional remote controldevice for the mobile device, and does not itself enable any additionalfunctionality.

Mobile devices are also used to store user specific information. Thisuser specific information can include information controlling modes ofoperation of the device, the arrangement of data and applications, andthe implementation of various filters that control the user experienceand/or the capabilities of the associated mobile device. Users of mobiledevices therefore increasingly expect a consistent experience acrossapplications. Accordingly, extending a user interface that implementssuch user preferences to other devices would be an advantage.

SUMMARY

Embodiments of the present invention are directed to solving these andother problems and disadvantages of the prior art. In accordance withembodiments of the present invention, systems and methods forassociating or pairing a mobile device with an output device included aspart of an interactive system are provided. More particularly,embodiments of the present invention enable the application of userpreferences associated with the mobile device to the operation of theoutput device and/or the interactive system. In general, the mobiledevice is provided with a mobile application or mobile app, and isregistered with a mobile connect server. In order to initiate pairing,the user enters a request for a pairing code via the interactive systemor equipment. In response to the request, the mobile connect serverreturns a pairing code that is displayed or otherwise output to the userby the output device. The user then enters the pairing code in themobile app on their mobile device. The mobile app returns the enteredpairing code to the mobile connect server. In response to a matchbetween the pairing code provided to the interactive equipment foroutput to the user and the pairing code entered in the user's mobiledevice and provided to the mobile connect server, the mobile device ispaired to the interactive system. The user can then implement theapplication of user preferences associated with the mobile device by theinteractive system. In addition, the user can access personalizedcontent, order other available content, and/or authorize payment forcontent or services.

A system in accordance with embodiments of the present invention caninclude a mobile device running a mobile application. The mobile devicecan be capable of operating as an endpoint of a communication linkbetween the mobile device and the mobile connect server. Communicationsbetween the mobile device and the mobile connect server can be overvarious networks, such as a wireless carrier network, a wireline carriernetwork, a wireless or wireline local area network, and a wireless orwireline wide area network, including but not limited to the Internet.The mobile connect server is interconnected to a plurality of roominteractive or entertainment systems that include terminal or outputdevices. This connection can be established over the Internet, and/or aproprietary network. In accordance with still other embodiments, a localclient server can be interposed between the mobile connect server and atleast some of the room output devices. As an example, a local clientserver can comprise a headend system that operates to provide selectedprogramming to interconnected interactive or output devices at a hotelor other property having a number of output devices.

The mobile device is generally associated with user preference data orinformation. Such user preference data can be stored on the mobiledevice. Alternatively or in addition, user preference data associatedwith the mobile device can be stored on a device other than the mobiledevice that is accessible to the user over a communication link. Forinstance, the mobile application can utilize the communication link toaccess the user preference data. As a further example, user preferencedata stored on a device other than the mobile device can be accessedafter user permission has been obtained, for example through a suitableauthorization granted by the mobile application. The user preferencedata can be applied to control various aspects of the user experience orinterface presented to the user by the interactive system. As aparticular example, but without limitation, user preference data caninclude information controlling the data sources available throughinteractive systems or equipment after the mobile device has been pairedto an output device associated with the interactive system or equipment.For instance, the user preference data can act to block the receipt oftelevision channels or other sources of information that the user doesnot want to have available. The user preference data can also be used todetermine a channel lineup or ordering. As a further example, the userpreference data can provide subscription information to enable thereceipt of premium content available under a subscription plan. Inaccordance with still other embodiments, the user preference data caninclude payment information to enable the receipt of pay per view orother premium content without requiring or while reducing the amount ofmanual input required by the user to access such content.

Methods in accordance with embodiments of the present invention includeinitiating a request for a pairing code for use in association with aselected terminal or output device. The request is sent to a mobileconnect server, which responds with a pairing code. The returned pairingcode is displayed or otherwise output to a user. The pairing code isthen entered into a mobile application running on a user's mobiledevice. Entering the pairing code in the mobile application can includemanual entry of the pairing code by the user in the mobile device. Asanother example, entering the pairing code can include scanning orphotographing a representation of the pairing code comprising, forexample a bar code or a quick response (QR) code. The mobile app in turndelivers the entered pairing code to the mobile connect server. Deliveryof the pairing code to the mobile connect server can be accomplishedusing a communication link established between the mobile device and themobile connect server. The communication link between the mobile deviceand the mobile connect server can include but is not limited to acarrier wireline or wireless network, a Wi-Fi or wireline Ethernetnetwork, or combinations of network types and protocols. In response toreceipt of a pairing code that matches the pairing code output by theterminal device, the mobile device is associated with or paired to theoutput device. In response to a valid pairing, various information canbe displayed to the user by the mobile device, such as menus, channelguides, interactive program guides, and the like. Moreover, selectionsmade by the user through the mobile device with respect to programmingand/or other services can control operation of the output device.

Additional features and advantages of embodiments of the presentinvention will become more readily apparent from the following detaileddescription, particularly when taken together with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts elements of a system incorporating a mobile deviceinterface in accordance with embodiments of the present invention;

FIG. 2 is a block diagram depicting components of a system in accordancewith embodiments of the present invention;

FIG. 3 is a flowchart depicting aspects of the operation of a system inaccordance with embodiments of the present invention;

FIG. 4 depicts exemplary screenshots provided by a mobile application inaccordance with embodiments of the present invention;

FIG. 5 is a flowchart depicting additional aspects of the operation of asystem in accordance with embodiments of the present invention; and

FIG. 6 illustrates an example channel lineup resulting from theapplication of user preference information in accordance withembodiments of the present invention.

DETAILED DESCRIPTION

FIG. 1 depicts elements of a system 100 that enables and supportspairing of a terminal or output device with a mobile application inaccordance with embodiments of the present invention. The system 100generally includes a central server system 104, a local client system108, and a mobile device 112. The mobile device 112 is generallyassociated with a user 116. Optionally, the system 100 can include auser data store 118 and/or a mobile application server 120 that areseparate from the mobile device 112. These system devices or nodes 104,108 and 112 can be interconnected by one or more networks 122. Moreover,different networks 122 can interconnect different nodes 104, 108 and112.

The central server system 104 generally includes a mobile connect server124. As described in greater detail elsewhere herein, the mobile connectserver 124 operates as a central or control node in pairing a terminalor output device, hereinafter referred to as an output device 136 with amobile device 112 and with enabling control of aspects of the operationof the output device 136 in response to input provided at the mobiledevice 112. Optionally, the central server system 104 can also include adata server 128. The data server 128 can provide various data andinformation to other components or nodes of the system 100, for examplevia the mobile connect server 124. Examples of such data include channellists, TV program data and interactive program guide information.

The local client system 108 is an interactive system typicallyassociated with a physical location, or a group of related physicallocation, such as a lodging or healthcare facility. Thus, in oneexemplary application, the local client system 108 can be associatedwith a hotel having any number of guest rooms. The local client system108 generally includes a site or local client server 132. The localclient server 132 generally functions as a headend for data andinformation provided by or in association with the central server system104. Moreover, the local client server 132 connects the local clientsystem 108 to the central server system 104. Although for ease ofillustration a single local client system 108 is illustrated in FIG. 1,a system 100 can include a plurality of local client systems 108interconnected to a common central server system 104. The local clientserver 132 is interconnected to an output device 136 via a local clientnetwork or distribution system 140. In particular, data and information,such as audio-visual content, interactive program guides, and the like,can be passed from the local client server 132 to the output device 136via the local client network 140. Input entered at the output device136, either directly or through a remote control or other device, suchas a wireless keyboard, associated with the output device 136 can bepassed back to the local client server 132 via the local client network140.

In addition to delivering content to an output device 136 and tohandling input associated with requests for content, the local clientserver 132 can perform various administrative tasks. Theseadministrative tasks can include associating charges, for example inconnection with lodging, healthcare or other guest based services, forpay per view content or other content or services associated withspecific charges to a room containing the output device 136 to which thecontent or service is delivered. In accordance with embodiments of thepresent invention, the local client network 140 can comprise an Internetprotocol network, some other digital network, and/or an analog network.Moreover, the local client network 140 can support radio frequency (RF)connections between the output device 136 and the local client server132, including wireline RF connections.

An output device 136 can include various audio-visual equipment,including but not limited to a high definition television, a standarddefinition television, a surround sound receiver, and/or speakers. Inaddition, an output device 136 can include an integrated terminalprocessor, a computer, and/or can be associated with a set top box orother separate component, to support two-way communications between theoutput device 136 and the local client server 132. Accordingly, theoutput device 136 can support the display of interactive menus andprogram guides, and the receipt of selections provided by a user orother user input that is relayed to the local client server 132. Userinput can be provided through keypads, touch screen displays, remotecontrol devices or the like provided as part of the output device 136,for example as part of a set top box, game console, or television.

The mobile or user device 112 generally includes a device that isassociated with a particular user 116. Examples of a mobile device 112include a smart phone, tablet computer, laptop computer, or other mobilecomputing device. Moreover, the mobile device 112 generally supportsexecution of a mobile application, as described in greater detailelsewhere herein. Although for ease of illustration and description asingle mobile device 112 and user 116 pair is illustrated in FIG. 1, asystem 100 can support multiple mobile devices 112 and associated users116.

The optional user data store 118 can be used to store or maintain user116 specific information. Such information can include user preferenceinformation or data, as described in greater detail elsewhere herein.The data stored on a user data store 118, if provided, associated with aparticular user 116 can be accessed by that user 116, for example afterauthorization received at the user data store 118 from a mobile device112. Moreover, authorization can include an instruction to provide userpreference data from the user data store 118 to a central data store 104or a local client system 108, either directly or through an associatedmobile device 112. The user data store 118 can, for example, comprise ageneral purpose computer and/or a network attached data storage system.

The optional mobile application server 120 can handle various duties,such as the delivery or download of a mobile application to the mobiledevice 112 to facilitate interconnection and interoperability of themobile device 112 with the remainder of the system 100. If provided, amobile application server 120 can also handle registration of aparticular mobile device 112 and/or user 116 with the system 100. Otheroperations that can be provided or supported by a mobile applicationserver 120 include providing information concerning the programming orother amenities available at properties having compatible propertymanagement systems 108, for example in the vicinity of the mobiledevices 112 current location, or at a location selected by the user 116.The mobile application server can also provide content for display onthe mobile device 112, including audio-video content, such aspromotional materials, advertisements, video on demand, or othercontent. Alternatively, such functionality and features can be providedby, for example, the mobile connect server 124.

In general, operation of the system 100 includes action by a user 116 todownload a mobile application on their mobile device 112. Downloadingthe mobile application can be through establishing a connection betweenthe mobile device 112 and a mobile application server 120 and/or amobile connect server 124. Downloading can include registration with amobile application server 120 and/or a mobile connect server 124. Afterinstalling and, if required by the particular implementation of thesystem 100, registering the mobile application, the user 116 has theoption of pairing their mobile device 112 with an output device 136, toenable control of the output device 136 using the mobile device 112,where such control interaction involves commands entered in the mobiledevice 116 that are passed through and/or processed by the centralserver system 104.

With reference now to FIG. 2, additional aspects and components of asystem 100 in accordance with embodiments of the present invention aredepicted. Each mobile device 112, mobile connect server 124, and localclient server 132 include a processor 204 and memory 208. The processor204 may comprise a general purpose programmable processor or controllerfor executing application programming or instructions. As a furtherexample, the processor 204 may comprise a specially configuredapplication specific integrated circuit (ASIC). The processor 204generally functions to run programming code or instructions, such asapplications or programs, implementing various functions of theassociated device or node 112, 124 or 132. As can be appreciated by oneof skill in the art after consideration of the present disclosure,different devices 112, 124 and 132 will typically have differentprocessors 204, depending on the functions and capabilities of theassociated device 112, 124 or 132. The memory 208 is generally used inconnection with the execution of application programming by theprocessor 204, and for the temporary or long term storage of programinstructions and/or data. As examples, the memory 208 may compriseremovable secure digital storage, RAM, SDRAM, or other solid statememory. Moreover, some or all of the memory 208 may be integral to theprocessor 204.

A device 112, 124 or 132 can also include data storage 212. Inaccordance with embodiments of the present invention, data storage 212can contain program code or instructions implementing variousapplications or functions executed by the associated device 112, 124 or132. Like the memory 208, the data storage 212 can comprise a solidstate memory device. In addition, in certain applications, the datastorage 212 can be integrated with and/or indistinguishable from thememory 208, for instance on certain mobile devices 112. Alternatively orin addition, the data storage 212 may comprise a hard disk drive orother random access memory, and can be integral to the associated device112, 124 or 132, or can be interconnected to the device, for example asnetwork attached storage.

A device or node 112, 124 or 132 can also be associated with one or moreuser input devices 216. Examples of user input devices 216 can includekeyboards, touch screen displays, position encoders such as a touchpad,mouse, or track ball, associated with a display, switches, or any otherdevice capable of receiving input from a user 116. In addition, a device112, 124 or 132 can be associated with one or more user output devices220. Examples of user output devices 220 include displays, speakers, andindicator lamps.

In addition, each node 112, 124 or 132 can include one or morecommunication interfaces 224. The type of communication interface orinterfaces 224 associated with a particular node 112, 124 or 132 istypically determined by the type of communication network 122 over whichthe associated node 112, 124 or 132 communicates. For example, in thecase of a mobile device 112, a communication interface 224 can includean interface to a wireline or wireless carrier network, including butnot limited to a cellular network, the public switched telephony network(PSTN), a satellite telephony network, or a wireline or wirelessInternet protocol network. Moreover, different communication interfaces224 can be used in different situations. For example, a mobile device112 can include a relatively short range wireless communicationinterface 224, such as a Bluetooth or Wi-Fi network interface 224, forinterfacing with an Internet protocol network 122. As another example, amobile device 112 can include one or more relatively long range wirelesscommunication interfaces 224, such as a cellular voice and/or datanetwork or other wireless carrier network communication interface 224.Moreover, some or all of the available communication interfaces 224 canbe used to interconnect a mobile device 112 including the communicationinterfaces 224 to a mobile connect server 124 or other node in thesystem 100. With respect to a mobile connect server 124 and/or a localclient server 132, a communication interface 224 can include an Ethernetor other Internet protocol communication interface 224, for example forinterconnecting to a network 122 comprising the Internet. As anotherexample, a communication interface 224 associated with a mobile connectserver 124 and/or a local client server 132 can include an interface toa proprietary satellite communication system. As can be appreciated byone of skill in the art after consideration of the present disclosure,different communication interfaces 224 can be used for different dataand/or situations. For instance, a broadband communication interface 224can interconnect a mobile connect server 124 to a telephony carrier'scommunication server for communicating with mobile devices 112 over acarrier wireless network. A broadband communication interface 224 to anInternet protocol network 122 connecting a mobile connect server 124 toone or more local client servers 132 can also be provided. As yetanother example, a communication interface 224 that enables satellitecommunications between a mobile connect server 124 and one or more localclient servers 132 can be provided.

Each node 112, 124 and 132 of a system 100 can be associated withdifferent applications or application programming. These differentapplications can be stored in the data storage 212 of the associatednode 112, 124 or 132. For instance, in the case of a mobile device 112,application programming can include a mobile app 228. As disclosedherein, the mobile app 228 can function to receive a pairing code thatthe mobile app 228 delivers to the mobile server system 124. Inaddition, the mobile app 228 can operate to display menus, channelguides, and interactive program guides or other information to a user116, and to receive input from a user 116 that is relayed to the mobileconnect server 124 for further action, such as to control the operationof a paired output device 136. The data storage 212 of the mobile device112 can also store data, such as user preference data or information230. As described in greater detail elsewhere herein, the userpreference data 230 can be applied to control aspects of the user 116experience. Moreover, in accordance with embodiments of the presentinvention, user preference data 230 can be applied by the mobile connectservers 124 and/or the local client server 132 to control aspects of theoperation of an output device 136 and/or the features, behavior or otheraspects of an interactive system with respect to the user 116 associatedwith an applied set of user preference data 230.

The mobile connect server 124 can store or maintain various applicationsand/or data in associated data storage 212. For example, global propertydata 232, including information received from interconnected localclient servers 132 regarding programming available from particular localclient servers 132 can be stored in data storage 212. As anotherexample, mobile server data 236 can include information regardingregistered mobile applications 228, and the current status of registeredmobile apps 228. In addition, mobile server data 236 can include userpreference data 230 for particular users 116 associated with registeredmobile applications 228. Alternatively or in addition, user preferencedata 230 can be stored on the mobile connect server 124 apart frommobile server data 236. Mobile server data 236 can also includeinformation identifying pairings between output devices 136 and mobiledevices 112. As yet another example, mobile server data 236 can includechannel guides, interactive program guides, movie schedules, TV showschedules, and the like in a format suitable for handling by a mobileapp 228. Mobile server data 236 can additionally include output device136 location information and/or location information for output devices136 that have been paired to mobile devices 112. This locationinformation can be stored as a latitude and longitude, an address of aproperty at which an output device 136 is located, and/or using otherlocation identifying information. An example of an acceptable format ofmobile server data 236 is an XML (extensible markup language) file. Asanother example, the data storage 212 of a mobile connect server 124 caninclude stored content 240. Stored content 240 can comprise generallyavailable on demand content. As another example, stored content 240 cancomprise content that is stored or recorded at the specific request of auser 116, for example for personal time shifting purposes. Accordingly,embodiments of the present invention can provide a virtual digital videorecorder (DVR) service. As another example, the data storage 212 of themobile connect server 124 can include a mobile server application 244.The mobile server application 244 can control various aspects andfeatures of the functionality of the mobile connect server 124 withrespect to interconnected mobile devices 112 and local client servers132. For instance, the mobile server application 244 can respond torequests for pairing codes, and can associate a particular output device136 with a particular mobile device 112 in response to receiving apairing code from the mobile device 112 that matches the pairing codeoutput by the output device 136. In addition, the mobile serverapplication 244 can operate to receive commands input at the mobiledevice 112, and to control a paired output device 136 and/or causecontent or other material to be delivered to an output device 136 and/ora mobile device 112 in response to such input. Other examples ofprogramming and data that can be maintained in the data storage 212 of amobile connect server 124 includes accounting data 248 that can tracktransactions and charges associated with a particular pairing and/ormobile device 112.

Examples of application programming and content that can be stored inthe data storage 212 associated with a local client server 132 includeslocal property data 252. Local property data can include informationregarding interconnected output devices 136, listings of stored and/oravailable content, location information related to the property orproperties with which the local client server 132 is associated, and/orlocation information related to individual output devices 136 associatedwith the local client server 132. In addition, stored content 256, suchas movies or other audio-visual content, can be maintained in the datastorage 212. The data storage 212 of the local client server 132 alsogenerally includes a local client server application 260. The localclient server application 260 can handle interaction between the localclient server 132 and the mobile or central server 124. In accordancewith embodiments of the present invention, the local client serverapplication 260 can also handle the delivery of pairing code informationto an output device 136, and the delivery of content and/or controlsignals to connected output devices 136 in response to commands receivedfrom the mobile or central server 124. The data storage 212 of the localclient server 132 can also include lodging or user stay information 264.Examples of user stay information 264 include records of transactionidentifiers assigned to guests and associations of such transactionidentifiers with one or more output devices 136, pairing codes, orsubsequent identification codes. User stay information 264 can alsoinclude user preference data 230 for users 116 who have paired a mobiledevice 112 to an output device 136 that is interconnected to the localclient server 132. Alternatively or in addition, user preference data230 can be stored on the local client server apart from the user stayinformation 264.

With reference now to FIG. 3, aspects of the operation of a system 100in accordance with embodiments of the present invention are illustrated.Initially, at step 304, a user 116 becomes aware of the availability ofthe mobile app 228, and downloads the mobile app 228. In accordance withat least some embodiments of the system 100, the user 116 may berequired to register the mobile app 228 as part of installing it on theuser's 116 mobile device 112 (step 304). The mobile app 228 can be madeavailable through various channels. For example, the mobile app 228 canbe made available by the central server system 104, a mobile applicationserver 120, a third party application provider, or other source.Typically, a user 116 will install the mobile app 228 to enable accessto various functions and information through the mobile device 112,including access to information regarding nearby properties that have alocal client system 108 that is compatible with the mobile app 228 andthat features desired programming or other services, to enable previewsof programming and views of channel guides and interactive programguides through the mobile device 112, to view services and features atparticular properties, and/or to enable the control of aspects of theoperation of a paired output device 136 through the mobile device 112.The mobile app 228 can also enable the application of user preferencedata 230 in controlling aspects of a user's 116 interaction with anoutput device 136 or other components or features of the interactivelocal client system 108, and/or with the central server system 132.

At step 308, the user 116 enters a selection to pair an output device136 with the user's mobile device 112. As an example, once opened, themobile app 228 can instruct the user 116 to turn on the output device136 (e.g., a television in a hotel room), push menu, and select mobileapplication from the menu. Selection of the mobile app 228 item from themenu displayed by the output device 136 can cause a request for apairing code to be passed to the central server system 104. Moreparticularly, the output device 136 can send a signal to the localclient server 132, via the local client network 140. The local clientserver application 260 running on the local client server 132 associatesthe request with a transaction identifier, also referred to as aLodgeNet™ stay ID, that is assigned by the local client system 108 foruse in tracking transactions related to a particular room and/or guest(i.e., user) 116. The local client server 132 can then pass the requestto the mobile connect server 124 of the central server system 104 via acommunication channel established using an interconnecting communicationnetwork 122 or a direct communication link.

In response to receiving a request to pair at the central server system104, a pairing code is generated and returned to the local client system108 (step 312). In particular, the mobile server application 244 canoperate to generate a temporary code or pairing code that is associatedwith the transaction identifier provided with the request, and that isreturned back to the local client server 132. The local client server132 then operates to provide the pairing code to the output device 136from which the request was initiated, via the property distributionnetwork 140. In addition, the mobile server application 244 can cause arecord to be created associating the pairing code and the transactionand identifier and that is stored as part of mobile server data 236.Notably, neither the local client system 108 nor the central serversystem 104 is required to have information regarding the identity of theuser 116 or mobile device 112, at least at this point in thetransaction. The output device 136 displays or otherwise outputs thepairing code to the user 116 (step 316). The pairing code can bedisplayed as a user friendly series of characters. As an example, andwithout limitation, the pairing code can comprise a six digit number.Alternatively or in addition, a pairing code can comprise a computerreadable code, such as a barcode or a quick response (QR) code that canbe captured by a camera or scanner provided as part of or in associationwith the mobile device 112. As yet another example, a camera included inthe mobile device 112 can capture the pairing code and apply opticalcharacter recognition. At step 320, the pairing code is entered in themobile device 112, for example in a data entry field provided by themobile app 228, and is sent to the central server system 104 via acommunication network 122. Accordingly, entry of a pairing code caninclude manual entry of that pairing code by the user 116 into themobile device 112 via a user input 216 provided as part of the mobiledevice 112. Alternatively, entry of the pairing code in the mobiledevice 112 can include the capture of a machine readable code throughoperation of a suitable capture facility provided by the mobile device112 in response to commands entered by the user 116. Notably, theprovision of a pairing code by the output device 136 that is entered orcaused to be entered in a mobile device 112 by a user 116 is the onlydirect communication required between the output device 136 and themobile device 112. Moreover, the pairing code can be transmitted fromthe mobile device 112 to the mobile connect server 124 of the centralserver system 104 using a network 122 that is separate from the network122 interconnecting the central server system 104 to the local clientsystem 108. Accordingly, a communication channel interconnecting themobile device 112 to the mobile connect server 124 can be completelyseparate from a communication channel interconnecting the mobile connectserver to the local client server 132 and/or the output device 136.

At step 324, a determination is made by the mobile connect server 124 asto whether a valid pairing code has been received. If a valid pairingcode has not been received, the system can return to step 308, to waitfor a further request to pair an output device 136 to a mobile device112. If a valid pairing code is received, the mobile connect server 124pairs the mobile device 112 from which the pairing code was receivedwith the output device 136 that displayed the pairing code (step 328). Arecord of this pairing or association can be maintained in the mobileserver data 236.

After a mobile device 112 has been paired to an output device or roomterminal 136, the mobile device 112 can be used to control aspects ofthe operation of the output device 136. For example, the programming orother content or information displayed by the output device 136 can becontrolled in response to input entered by the user 116 at the mobiledevice 112. In accordance with further embodiments, volume and otheroperating parameters of the output device 136 can be controlled throughinput entered at the mobile device 112.

The central server system 104 can continually monitor for input receivedfrom the mobile device 112, and in particular the mobile application 228running on the mobile device 112 (step 332). Where input received from apaired mobile device 112 affects the output of the output device 136,for example in the form of a request to view a particular channel oritem of content, the mobile connect server 124 can provide the requestedcontent, for example a program from stored content 240 or an interactiveprogram guide, from content stored on the central server system 104.Alternatively, the mobile connect server 124 can command the localclient server 132 to stream content 256 stored by or in association withthe local client server 132 to the output device 136, or to “tune” theoutput device 136 to a particular broadcast channel, etc. As yet anotherexample, the input from the paired mobile device 112 can include inputdirecting the output device 136 to output content provided by the mobiledevice 112 that is passed to the output device 136 through the mobileconnect server 124 (step 336). After providing requested content orafter determining that the input is not received from the mobile device112, a determination can be made as to whether a new request to pair themobile device 112 with an output device 136 is received (step 340). Ingeneral, a new request is received when a new pairing code is entered inthe mobile application 228 of a mobile device 112, and where the newpairing code was generated in connection with a request from a newoutput device 136. In response to the receipt of a new pairing code froma previously paired mobile device 112, the original pairing can beterminated (step 344).

At step 348, a determination may be made as to whether a request toterminate pairing has been received by the mobile connect server 124. Arequest to terminate pairing can be initiated by a user 116 via themobile app 228 running on the mobile device 112. A pairing can also beterminated when the user associated with a pairing checks out of orleaves the property at which the paired output device 136 is located. Arequest to terminate pairing can also be in the form of a request for apairing code associated with the output device 136 that is alsoassociated with a new transaction identifier. For example, a newtransaction identifier can be used for a room that the output device 136is associated with when the room is assigned to a new guest. As yetanother example, termination of pairing can result from revocation ofthe transaction identifier associated with a pairing. If a request toterminate pairing is received, that previous pairing is terminated (step344). The process may then end. So long as a condition resulting in thetermination of an established pairing is not received, the process cancontinually check for input from a mobile device (step 332) and canprovide content (step 336) as appropriate in response to received input.

In accordance with further embodiments of the present invention, pairingcodes can expire after some predetermined period of time. In addition,the relatively short pairing code can be replaced by a longer pairingkey that is exchanged automatically (i.e., without requiring manualentry or action by the user 116) after a successful pairing event, toenable the use of user friendly pairing codes, while providing anability of the system 100 to service a large number of output device 136and mobile device 112 pairings.

Although examples have been described in which a mobile device 112 ispaired to a single output device 136, embodiments of the presentinvention can support simultaneous pairing of a mobile device 112 tomultiple output devices 136. For example, with respect to a room or asuite having multiple televisions or other output devices 136, a mobiledevice 112 can be paired to those output devices 136 simultaneously. Inaccordance with still other embodiments, a pairing code output by afirst output device 136 in a room or an associated room can be used topair a mobile device 112 to a second output device 136 in the room or anassociated room.

FIG. 4 is a set of screenshots illustrating output displayed by a mobileapp 228 in accordance with exemplary embodiments of the presentinvention. In an initial or welcome screen 404, a top level menu 404 canbe presented to the user 116. The top level menu 404 can display aseries of options, such as an option to browse movies 408, access freemobile content 412, access a program guide 416, or access other services420. In addition, the option to pair to a TV 424 (i.e., to an outputdevice 136) can be presented. In accordance with at least someembodiments, the top level menu 404 can be accessed and can present atleast some options even in the absence of a successful pairing. Forexample, free mobile content 412, programming guides 416, and otherservices 420 can be at least partially available in the absence of acurrent pairing between a mobile device 112 and an output device 136.Accordingly, the mobile device 112 through execution of the mobile app228 can be used to view programming options, for example by location,property, time and date, or other parameter or set of parameters, or toaccess other services and features, even when the mobile device 112 isnot paired with an output device 136.

In response to a selection of the option to pair the mobile device 112to a TV 424, the mobile app 428 can display a pairing screen 428. Thepairing screen can provide instructions for completing pairing betweenthe mobile device 112 and an output device 136. In addition, a field 432can be provided in which a pairing code displayed to the user 116 by anoutput device 136 can be entered by the user 116. After the successfulentry of a valid pairing code, additional features or options can beenabled. For example, in response to entry of a valid pairing code, themobile device 112 can again display the initial or welcome screen 404,and certain options that were previously inactive, such as a browsemovies option 408 is now active. Alternatively or in addition,additional categories or options can be presented.

In response to a selection of the browse movies item 416, movie listings436 can be presented. The movies included in the movie listings aregenerally movies available from the local client server 132 associatedwith the output device 136 to which the mobile device 112 is paired. Inresponse to a selection of the free mobile content option 412, a listingof mobile content 440 can include listings of content available forviewing on the mobile device 112. In response to the selection of theprogramming guide option 416, a programming guide page 444 can bepresented to the user 116. The programming guide 444 generally containsprogramming that is accessible through the paired output device 136. Theselection of the other services option 420 presents another servicespage 448 to the user 116. Examples of other services include contentthat has been recorded for personal time shifting purposes by the user116. In connection with recorded material, the user 116 can order orotherwise arrange for the recording of selected content, for examplethrough a request that is provided to the central server system 104.Moreover, such a request can be made via an interface provided by themobile app 228. The interface for ordering the recording of specifiedcontent can be provided by the other services page 448. Moreover, thatcontent can be ordered through the other services page 448. The recordedcontent can be maintained at the central server system 104, and can bedelivered to the local client server 132 associated with the outputdevice 136 to which the mobile device 112 is paired. Moreover, thedelivery to the local client server 132 of recorded content can beinitiated after the appropriate local client server 132 for delivery ofthe recorded content to the user 116 has been identified, for example inconnection with a successful pairing operation, or in response to arequest for that content, for example through a command entered usingthe mobile app 228.

In accordance with other embodiments, a mobile connect server 124 maycomprise a server having a well known address that can be contacted by amobile app 228. In accordance with further embodiments of the presentinvention, a mobile app 228 can establish communication with a localclient server 132 directly, rather than through a mobile connect server124. In accordance with still other embodiments, a mobile connect server124 can communicate with output devices 136 without requiring anintervening local client server 132.

In accordance with embodiments of the present invention and as describedherein, information regarding the location of a mobile device 112 and/oran output device 136 paired to a mobile device 112 can be used toprovide relevant information to a user. For example, a set of movielistings 436 and/or a programming guide 444 can be tailored to includeonly those listing available at the current location of the mobiledevice 112 and/or the location of the property including the outputdevice 136 with which the mobile device 112 is paired. In addition, thelocation of a mobile device 112 can be used to provide that mobiledevice 112 with other services 448 that require or that can benefit fromthe location information. In accordance with embodiments of the presentinvention, the location of the mobile device 112 can be determined basedon the pairing of the mobile device 112 with an output device 136. Inparticular, embodiments of the present invention include a mobile serverapplication 244 that has or can access the location of an output device136 paired with a mobile device 112. From the location of the outputdevice 136, the location of the mobile device 112 can be inferred, evenif the user of the mobile device has disabled conventional locationservices or has otherwise declined to provide location information. Inaccordance with still other embodiments, the location informationderived from the location of a paired output device 136 can be providedto the mobile app 228 running on or associated with the mobile device112 paired with that output device 136. The mobile app 228 can then usethe location information in connection with location based services,even if the user of the mobile device 112 has disabled other locationservices.

FIG. 5 is a flowchart depicting further aspects of the operation of asystem 100 in accordance with embodiments of the present invention.Initially, at step 504, the user 116 selects an option to add userpreference data 230 in connection with a mobile application 228. Theuser 116 then enters user preference data 230 (step 508). The selectionof the option to add user preference data 230 can be made throughinteraction by the user 116 with the mobile application 228.Accordingly, the entry of user preference data 230 can be made inconnection with a user input 216 provided by a mobile device 112 runningin mobile application 228. Alternatively or in addition, the entry ofuser preference data 230 for association with a mobile application 228can be made through another device, and that user preference data 230can then be loaded onto the mobile device 112 of the user 116. Moreover,the entry of user preference data 230 can be independent or in theabsence of a pairing between a mobile device 112 and an output device136. In addition, although user preference data 230 can be stored inmemory 208 and/or data storage 212 associated with a mobile device 112,embodiments of the present invention also can include storage of userpreference data 230 in a user data store 118 that is separate from themobile device 112. Moreover, user 116 can store user preference data 230on multiple mobile devices 112, and/or can access user preference data230 stored in a user data store 118 accessible to one or more mobiledevices 112 over a communication network 122, for application by one ormore mobile devices 112 running a mobile app 228 as described herein. Auser 116 can also create multiple sets of different user preference data230. For example, a user 116 may define a first set of user preferencedata 230 to use during business travel, and a second set of userpreference data 230 to use during vacation travel.

After the entry of user preference data 230, a determination can be madeas to whether the mobile device 112 associated with user preference data230 has been paired to an output device 136 (step 512). If pairing hasbeen completed, a determination can next be made as to whether the userpreference data 230 should be provided to the mobile connect server 124and/or the local client server 132 for application in connection withthe operation of the output device 136 and the interaction between themobile device 112 and the output device 136 and/or the interactive localclient system 108 (step 516). The determination as to whether to senduser preference data 230 can be made with reference to user selectionsthat have been made with respect to the operation of the mobile app 228.A user 116 can also manually control the provision of user preferencedata 230 to other nodes in the system 100. Moreover, automatic or manualcontrol can be applied in connection with selecting a particular set ofuser preference data 230 to apply, determining whether an entire set ofuser preference data 230 is to be applied, determining whether to applyportions of user preference data 230, and determining whether anindividual item of user preference data 230 is to be applied. If userpreference data is not sent to the mobile connect server 124 or thelocal client server 132, the system 100 operates normally (e.g., itapplies its default configuration or an administered configuration),without modification by user preference data 230 (step 520).

If user preference data 230 is provided to the mobile connect server 124and/or the local client server 132, the user preference data 230 can beapplied to control aspects of the user experience or interaction withrespect to the output device 136 and the associated interactive system(i.e., the local client system 108 and/or the central server system 104)(step 524). As an example, the channel lineup available through theoutput device 136 can be modified as compared to the channel lineupavailable in the absence of the user preference data 230. Examples ofmodifications include blocking channels that the user 116 does not wishto access, enabling channels that the user 116 does wish to access,altering channel lineups to arrange available channels in a preferredorder, selecting a preferred default or power on channel, selecting apreferred language for audio output and/or subtitles, etc. With respectto enabling certain channels, user preference data 230 can includesubscription or billing information to enable channels that are notoffered on a free to guest basis. As still other examples, userpreference data 230 can enable virtual channels that a user 116 can useto access personal data, including programs recorded as a result of theimplementation of a virtual digital video recorder (DVR) function of thesystem 100, access to data stored on the mobile device 112, or a server118, 120, or access to data stored on or available from otheraddressable data sources. Application of the user preference data 230can be by the central server system 104 and/or the local client system108. Moreover, the user preference data 230 can include instructions tocontrol aspects of the operation of a mobile device 112 and/or aninterface with components of the central server system 104 and/or thelocal client system 108.

At step 528, a determination can be made as to whether a selection toalter user preference data 230 has been entered. If such a selection hasbeen made the process can return to step 508, where the altered userpreference data is entered. If a selection to alter preference data hasnot been received, a determination can next be made as to whether theprocess should continue (step 532). If the process is to continue, itcan return to step 512. Alternatively, the process can end.

FIG. 6 illustrates an example channel lineup 604 available to a user 116through an output device 136. More particularly, the channel lineup 604in this example includes alterations based on the application of userpreference data 230 as described herein. More particularly, a number ofchannels are identified by name 608 and display number 612. The namedchannels 608 represent television channels or other sources ofinformation available at a paired output device 136 associated with aparticular local client system 108. The display channel 612 indicatesthe numerical channel to which the output device 136 should be tuned toaccess the associated named channel 608. A column of channel mask data616 indicates whether a particular channel 608 is actually available tothe user 116. In particular, channels marked with a bullet point (•) areavailable to this user 116 through the associated output device 136 bydefault, and can be selected by, for example, the facility at which theoutput device 136 is located. Channels for which no marking is includedin the associated channel mask 616 field could be viewed on theassociated output device 136, but are not accessible by default.Accordingly, such channels need to be added, for example through asubscription or on a pay per view basis. Channels having an X in theassociated channel mask 616 field are blocked as a result of theapplication of user preference data 230. As an example, a user 116 canchoose to block individual channels, for example as a way to implementparental controls. Channels for which an asterisk (*) is shown in thechannel mask indicate channels that are not available by default, butthat have been added as a result of the application of user preferencedata 230. For example, a user 116 may subscribe to particular channels,in which case information regarding the user's 116 subscription can beincluded in the user preference data 230. That subscription informationcan then be applied to make such channels available through a pairedoutput device 136. Accordingly, user preference data 230 can be used tocontrol the channels available through a paired output device 136. Userpreference data 230 can also be used to provide information required toaddress user 116 specific information. For example, through a reservedchannel provided by the local client system 108, a user can access avirtual DVR containing recorded programming. As a further example, userpreference data 230 pointing to an Internet or other address accessiblethrough the local client system 108 containing user 116 specificinformation, such as user data stored on the mobile device 112, or someother node within the system 100, can be delivered to the output device136. Accordingly, the user preference data 230 can be used to providethe user 116 with access to various sources of information, and toprovide the user 116 with a consistent user experience across differentlocal client systems 108 and output devices 136.

User preference data 230 can therefore be used to control variousaspects of the user 116 experience in connection with an interactivesystem such as a local client system 108 and associated output devices136. In addition to controlling available channels, user preference data230 can be applied to control the display number at which channels arelocated, the channel initially displayed when an output device 136 ispowered on, user alarm settings, the provision of subscriptioninformation necessary to access subscription television channels,payment information necessary to access pay per view channels, access tosources of information available from network nodes or other connecteddevices, and the like.

The foregoing discussion of the invention has been presented forpurposes of illustration and description. Further, the description isnot intended to limit the invention to the form disclosed herein.Consequently, variations and modifications commensurate with the aboveteachings, within the skill or knowledge of the relevant art, are withinthe scope of the present invention. The embodiments describedhereinabove are further intended to explain the best mode presentlyknown of practicing the invention and to enable others skilled in theart to utilize the invention in such or in other embodiments and withvarious modifications required by the particular application or use ofthe invention. It is intended that the appended claims be construed toinclude alternative embodiments to the extent permitted by the priorart.

1. A method, comprising: receiving user preference data; storing thereceived user preference data; generating a first pairing code using afirst server, wherein the first server is interconnected to a pluralityof output devices at different geographic locations; communicating usinga first output device included in the plurality of output devices thefirst pairing code to a first user device; after communicating the firstpairing code to the first user device, receiving the first pairing codeat the first server; in response to receiving by the first server thefirst pairing code communicated from the first user device, associatingthe first user device with at least one of the first output device and asecond output device; providing the stored user preference data to atleast one of the first server and a second server; applying the userpreference data by the at least one of the first server and the secondserver.
 2. The method of claim 1, wherein communicating using a firstoutput device the first pairing code to the first user device includes:displaying the first pairing code to a first user using the first outputdevice.
 3. The method of claim 2, wherein communicating using a firstoutput device the first pairing code to the first user device furtherincludes: the first user entering the first pairing code in the firstuser device.
 4. The method of claim 1, wherein the first pairing code istransmitted from the first user device to the first server over anetwork that includes a wireless carrier network.
 5. The method of claim1, further comprising: receiving at the first server a first request fora pairing code, wherein the first request for a pairing code isassociated with a first transaction identifier and at least one of afirst output device identifier, a first property identifier, a firstroom identifier, and a first user device identifier, and wherein thefirst server generates the first pairing code in response to the firstrequest for a pairing code.
 6. The method of claim 5, wherein the firstrequest for a pairing code is associated with at least a first userdevice identifier, wherein the first user device is registered with thefirst server.
 7. The method of claim 5, further comprising:disassociating the first user device and the first output device inresponse to receiving at the first server a second request for a pairingcode, wherein the second request for a pairing code is associated with asecond transaction identifier and at least one of the first outputdevice identifier, the first property identifier, and the first roomidentifier.
 8. The method of claim 5, wherein the first pairing codeexpires after a first predetermined time has elapsed since the firstrequest for a pairing code was received at the first server.
 9. Themethod of claim 1, further comprising: after associating the first userdevice with a first output device, receiving a request for first outputfrom the first user device at the first server; and displaying the firstcontent using the first output device.
 10. The method of claim 1,further comprising: registering the first user device with the firstserver; receiving by the server an instruction contained in the userpreference data to make first content available; after associating thefirst user device with a first output device, receiving a request forthe first content from the first user device at the first server;displaying the first content using the first output device.
 11. Themethod of claim 1, further comprising: retrieving a stored location ofthe at least one of the first output device and the second outputdevice; applying the stored location as a location of the first userdevice.
 12. A system, comprising: a plurality of output devices; a firstmobile device; a mobile connect server, including: memory; applicationprogramming, wherein the application programming is stored in thememory; a processor, wherein the processor is operable to execute theapplication programming; a communication interface, wherein the mobileconnect server is interconnected to the plurality of output devices byat least a first network, wherein the application programming isoperable to provide a first pairing code to a first output deviceincluded in the plurality of output devices using the at least a firstnetwork, wherein after providing the first pairing code a first outputdevice the application programming is operable to generate a firstcommand in response to receiving the first pairing code from the mobiledevice over at least a second network; a plurality of local clientservers, wherein the at least a first network interconnects the mobileconnect server to at least a first local client server included in theplurality of local client servers; a first local client network, whereina first local client server included in the plurality of local clientservers is interconnected to at least some output devices included inthe plurality of output devices by the first local client network; userpreference data associated with the first mobile device, wherein theuser preference data controls aspects of the operation of at least oneoutput device included in the plurality of output devices.
 13. Thesystem of claim 12, wherein the first command is received by the firstlocal client server, and wherein in response to receiving the firstcommand the first local client server delivers content to the firstoutput device.
 14. The system of claim 12, wherein the local clientnetwork is a part of the at least a first network, wherein the firstproperty management server includes a content store, and wherein thefirst content is delivered from the first local client server to thefirst output device over the local client network.
 15. The system ofclaim 14, wherein the first mobile device is associated with a firstuser, the first mobile device including: a communication interface; adisplay; a user input, wherein the first mobile device is interconnectedto the mobile server by the at least a second network, wherein themobile device is operable to receive the first pairing code through theuser interface, wherein the mobile device is operable to transmit thefirst pairing code to the mobile server using the at least a secondnetwork, wherein the mobile device is operable to receive and display acontent menu, wherein in response to an input at the user inputselecting an item included in the content menu the first mobile deviceis operable to send a content selection message to the mobile serverusing the at least a second network.
 16. The system of claim 15, whereinin response to receiving the content selection message the mobile serversends the first command to the first property management server.
 17. Thesystem of claim 12, wherein the first mobile device is associated with afirst user, the first mobile device including: a communicationinterface; a user input, wherein the first mobile device isinterconnected to the mobile server by the at least a second network,wherein the mobile device is operable to receive the first pairing codethrough the user interface, and wherein the mobile device is operable totransmit the first pairing code to the mobile server using the at leasta second network.
 18. A method for ordering content, comprising:receiving at a mobile connect server a request to pair a first outputdevice with a first mobile device; providing by the mobile connectserver a first pairing code to the first output device; presenting bythe first output device the first pairing code to a user of the firstmobile device; entering by the user the first pairing code in the firstmobile device; sending the first pairing code from the first mobiledevice to the mobile connect server; in response to receiving the firstpairing code sent from the first mobile device at the mobile connectserver, the mobile connect server issuing a first pairing key to thefirst mobile device, and associating the first output device and thefirst mobile device; providing user preference data; storing the userpreference data; applying the user preference data to control aspects ofthe operation of the output device.
 19. The method of claim 18, furthercomprising: displaying an option on the first output device to pair to amobile device; receiving user input at the first output device selectingthe option to pair with a mobile device; sending the request to pairwith a mobile device from the first output device to the mobile connectserver.
 20. The method of claim 19, further comprising: providing aninteractive menu from the mobile connect server to the first mobiledevice, wherein the interactive menu includes a first menu item;receiving by the first mobile device a selection by the user of thefirst menu item; in response to the selection of the first menu item bythe user, the mobile connect server causing content related to the firstmenu item to be displayed on the first output device.